home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 43 lines | [TEXT/GEOL] |
- Item 4876673 29-Aug-90 11:26PDT
-
- From: BBSF.DEV Babcock & Brown, Michael Harper,AST
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: Design Question
-
- Attn: MacApp Developers
- SentBy: michael
- From the Cluttered Mind of Michael J. Harper...
- Design Question 8/29/90 10:56 AM
- (Please note, this is my first MacApp application, and, of course, I haven't
- been to MacApp University yet. Please be gentle.)
-
- I am building a front end to a relational database using MacApp. There is a
- two-level hierarchy to the data that needs to be presented. For example,
- there is a company, and the company may have any number of: 1) comments, 2)
- contacts, 3) offices.
-
- It seems reasonable to me that the company would be a descendant of TDocument
- and would have a view that displays the company's one-to-one information, i.
- e. its name. It also seems reasonable that the comments, contacts, etc.
- should be descendants of TDocument because the comments etc. have data and
- view(s) in their own right. However, they have a strong relationship with
- the parent company, so maybe the comments, etc. need to be presented in
- subviews of the parent company in order that event and command processing get
- taken care of cleanly, e. g. closing the company would close all the comments
- etc. for that company.
-
- I can see future applications with similar structure, so I'd like to get off
- to a good start the first time.
-
- This is my first MacApp application, so please don't be afraid to talk down to
- me!
-
- Thanks.
-
- Michael J. Harper
- Babcock & Brown
- BBSF.DEV
-
-